Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(runtime/testing): false positive for timers when an error is thrown #9553

Conversation

caspervonb
Copy link
Contributor

@caspervonb caspervonb commented Feb 20, 2021

Fixes #8954

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@caspervonb I just run provided test case on main branch and it results in exactly same output from deno test. I think this solution is preferable but we need another test case that actually demonstrates what's being fixed

Copy link
Member

@bartlomieju bartlomieju left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks Casper, provided test case fails on main

@caspervonb
Copy link
Contributor Author

Oops I cleaned up that test a bit too much, until it wasn't testing anything.
Fixed up test fails all cases on 1.7.5

Screenshot 2021-02-22 at 12 10 19 AM

@bartlomieju bartlomieju merged commit eefd522 into denoland:main Feb 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Test case is leaking async ops when using clearTimeout inside finally block after not catching error
2 participants